ShareWare OnLine 2

home *** CD-ROM | disk | FTP | other *** search

/ ShareWare OnLine 2 / ShareWare OnLine Volume 2 (CMS Software)(1993).iso / games1 / finala21.zip / FINALAPP.DOC < prev next >

Wrap

Text File | 1993-03-01 | 69KB | 1,806 lines

────────────────────── Final Approach v.2.1 ────────────────────── The electronic instrument approach plate atlas for use with PC-based flight simulators written by Georges Lorsche copyright (C) 1993 by Georges Lorsche, all rights reserved. ────────────────────────────────────────────────────────────────── ────────────────────────────────────────────────────────────────── This computer software is protected by copyright laws and international treaty provisions. It may not be sold or otherwise used for commercial benefit without the author's written permission. Modification of the program code, the documentation file or the eventual registration key file is prohibited. The non-registered version of Final Approach may be freely copied and shared. Distribution of a registered version is strictly prohibited. Users of Final Approach are encouraged to distribute the Instrument Approach Plates they create, provided that they do not charge for it and that Final Approach is mentioned in the documentation accompanying the files. Evaluation version and license: ─────────────────────────────── Final Approach is distributed as an evaluation version. It is fully functional in its capabilities to design and save realistic Instrument Approach Plates (IAPs). One single limitation applies: whenever you load an IAP from disk, only the map view of that IAP will be displayed. The profile view will always show the same, standard approach profile. Upon registration users will receive a special license key by mail or email. Entering this license key will instantaneously provide complete functionality to the program. -- page 2 -- Contacting the author ───────────────────── by mail: Georges Lorsche 5, rue des Violettes L-3447 Dudelange Luxembourg/Europe by fax: +352 459210 via CompuServe: Georges Lorsche 100041,211 Internet: 100041.211@compuserve.com The author is an active member of the Luxembourg Comnet BBS. If you are no CompuServe or Internet member, you may leave messages or inquiries on the Comnet Board: line 1 +352 466893 (14400 bps, V32bis) line 2 +352 467516 ( 2400 bps) line 3 +352 222534 (14400 bps, HST/V32bis) FILES ───── The distribution kit consists of the following files: WHATSNEW. Additions made since the last release FINALAPP.EXE Final Approach executable program FINALAPP.HLP Final Approach help file FINALAPP.DOC this documentation REGISTER.FRM registration form *.IAP sample Instrument Approach Plates -- page 3 -- Revision history ──────────────── Version 1.0 (Nov 11 1992) Basic version with plan view only Version 2.0 (Feb 1 1993) adds profile view adds snap to grid adds online help old IAPs remain compatible Version 2.1 (Mar 1 1993) compiled with Visual Basic 2.0 autostarts Windows when run from DOS fixes map view <Copy to Clipboard> bug adapts the Circle-to-land categories to the new U.S. TERPS standard expands the context-sensitive help system and maps help to the F1 key adds detailed IAP info to Load File dialogue adds FS airport coordinates and required scenery memo to printed IAP adds fully automatic morse code generation to navaid boxes adds holding symbol adds possibility to attach lines to holding fix adds free placement of intersections adds multiline free text, now allowing 72 lines per IAP (up from 24) adds capability to remove any IAP element any time adds restore function to the <Undo> button adds standard 3° descent guideline to profile view grid adds color output on adequate printers adds "show numbers" checkbox to profile view "Show numbers" now displays running number of all multiple elements Cant Angle between -40° and 40° is now accepted old IAPs remain compatible -- page 4 -- Documentation overview ────────────────────── The Final Approach documentation is organized as follows: page 1. About Final Approach .......................................... 5 2. Features ...................................................... 6 3. Non-registered version limitations ............................ 7 4. How to register ............................................... 7 5. Registration discount ......................................... 8 6. News and updates .............................................. 8 7. A few words about instrument approaches ....................... 9 8. Setting up Final Approach ..................................... 11 9. Running Final Approach ........................................ 11 10. Quick start ................................................... 12 11. The buttons explained ......................................... 13 12. Design buttons - Plan View .................................... 13 13. Design buttons - Profile View ................................. 21 14. Right-hand buttons ............................................ 27 15. Checkboxes .................................................... 30 16. Hints and tips ................................................ 31 17. Designing consistent Instrument Approach Plates ............... 32 18. File format ................................................... 33 19. Comments ...................................................... 35 20. Disclaimer .................................................... 35 -- page 5 -- About Final Approach ──────────────────── Most modern flight simulators have reached a level of realism that makes the use of real-world Instrument Approach Plates (IAPs) almost a necessity. Unfortunately, only few charts are generally included with these programs and the same is true for most of the currently available Scenery Disks. On the other hand, countless ASD-Sceneries and AAF-Adventures are waiting to be downloaded from Bulletin Board Systems all around the world. Again, these sometimes excellent productions would strongly gain in interest and usability if their designer had found a way to include digitized Instrument Approach Plates with his files. These were the reasons for developing Final Approach. With Final Approach you will display and, if you wish, design your own Instrument Approach Plates right on screen. You may also generate vectorized hardcopies in the highest resolution available on your printer. Unlike scanned IAPs, the plates you design with Final Approach are very economic in the disk space they use (only around 2K each) and can thus be very easily distributed. For obvious reasons, the IAPs you generate are not to be used for real world navigation. -- page 6 -- Features ──────── Because the resolution of our current generation of monitors would hardly allow for a complete chart to remain easily readable on screen, Final Approach displays the plan and the profile view in two separate windows. The printing routines however will generate a single, realistic IAP with plan and profile view combined. Plan view: Available elements - 1 runway - 1 approach line with optional procedure turn, localizer and Middle Marker. - 1 Outer Marker - 3 VOR facilities - 3 NDB facilities - 1 holding - 3 intersections, on request automatically placed on the approach track - 6 connecting lines, starting at VORs, intersections or the holding fix - 12 formatted text strings of up to 256 chrs and 1 to 3 lines each - 6 navaid boxes to label VORs and NDBs, automatic morse code included - 1 rounded box to label ILS approaches, automatic morse code included Profile view: Available elements - 1 glidepath with 9 user definable segments - 1 glideslope symbol for ILS approaches - 2 symbols for Outer and Middle Marker - 1 VOR symbol - 1 NDB symbol - 3 intersection symbols - 12 text strings of up to 256 chrs each, 8-14 point, regular or bold - 6 intersection labels, automatically formatted - 4 altitude labels with automatic calculation & placement of alt. AGL - complete Missed Approach instructions, automatically formatted - decision height, circle-to-land altitudes fo categories A, B, C and D - timing table automatically calculated and formatted For your convenience: - Erase button to remove any IAP element anytime - Undo button to erase the last element drawn or restore the last element erased - Detailed info on highlighted IAP in Load File window - FS airport coordinates and "Required Scenery" memo printed below IAP - Checkbox to overimpose a grid on the drawing surface - Grid inset indicates 320x200 size for AAF PCX files,(plan view only) - Snap to grid - Checkbox to number all multiple elements on the IAP - Context sensitive help available (by pressing a button or F1) - Left border selectable before printing - Copy to Windows Clipboard to export to Paintbrush or similar - Color output on adequate printers -- page 7 -- Non-registered version limitations ────────────────────────────────── The non-registered version of Final Approach 2.1 provides the full set of design tools also featured by the licensed version. It lets you create complete Instrument Approach Plates, save them to disk and distribute them as such or together with your ASD-sceneries or AAF-adventures. One single limitation applies: While you can design and subsequently save and print both the map view and the profile view of your newly created approach plate, the unregistered version will not allow reloading the profile view of any IAP from disk. Regardless of the IAP you load, you will always see the same standard default profile in the profile window. This profile is not related to the loaded IAP and will be marked "demo only". So be careful when designing IAPs with an unregistered version of Final Approach. Once you have finished work on a new IAP, remember to print it immediately! You will not be able to reload (and possibly rework or reprint) the profile view later, unless you register your copy. How to register ─────────────── The license fee for Final Approach is 30$. A discount of 1$ is offered for every IAP you submit up to a 15$ rebate maximum. See the next section on registration discount for details. To register, send your exact name and address together with your payment or credit card information to one of the addresses indicated on page 2 of this documentation file. Please consider using the included registration form ("register.frm") for this purpose. Upon reception of payment you will be sent a personal license number. From the Final Approach startup screen, select <Enter license> and fill in the requested data exactly as it appears on your license sheet. Your name and license number will be saved to the file "register.key" created in your Final Approach directory. The program will immediately become fully functional. Your name and license number will be displayed upon each subsequent program startup and in the About window. -- page 8 -- Registration discount ───────────────────── A substantial registration discount of up to 50 (!) percent is offered to every user who designs and submits a couple of IAPs (worth 1$ each) from his local or preferred airports before registering. This somewhat unusual registration policy works towards rapidly making a lot of electronic approach plates available for everyone to use. And that, after all, is what this program is all about. The author is willing to coordinate the design process, collect the IAPs, bundle them into coherent sets and make them publicly available. This distribution will be absolutely free. You will find the IAP sets on the CompuServe FSFORUM and on aviation-related Bulletin Board Systems worldwide. On request, registered users will be mailed complete IAP collections for a nominal shipping fee. Applying for a registration discount: First communicate to the author which IAPs you are willing to design. The author will check that no other user has applied for the same IAPs and reply accordingly. After you have terminated your IAPs, submit them via email or postal service. For every at least standard quality IAP you will be given a 1$ rebate (up to a maximum of 15$). Delivering 15 acceptable IAPs will thus cut the 30$ registration fee in half. Note: The author reserves the right to refuse IAPs designed the quick and dirty way and clearly below standard quality. News and updates ──────────────── The primary source for information about Final Approach will be the CompuServe FSFORUM. This is the hot spot where you will find news, fixes and updated versions first. The author will daily scan the FSFORUM for discussion of bug reports, whishes and additional information. If you are a CompuServe member, type GO FSFORUM at any prompt to join this community of avid flight simulation and aviation enthousiasts. Once you have registered, your license number will remain valid through all future 2.x versions of Final Approach. When an updated version becomes available, you may download and license it without additional payment. To license a newly downloaded version, you needn't even go through the registration process again. Simply keep the old "register.key" file in the Final Approach directory. Final Approach will recognize you as a legitimate user and run up to full functionality immediately. -- page 9 -- A few words about Instrument Approaches ─────────────────────────────────────── Getting an aircraft in the air is generally pretty straightforward, getting it safely back to the ground is where the hard labour begins. For those of us who fly simulated aircraft, a well-planned approach and safe landing may be the most difficult, but often also the most rewarding part of every flight. Good, visual approaches and landings are very difficult to accomplish in a simulated flying environment on a PC. The lack of a feel for the aircraft movement through space, the rather primitive input devices, the absence of a 3D ground reference, the often low resolution of the screen are some of the factors that make a visual landing in a simulated aircraft an even greater challenge than landing the real thing. That is why most computer pilots tend to use instrument approach procedures wherever possible, even if the weather conditions would allow for a seemingly hassle-free visual landing at the destination airport. Those instrument approach procedures are carefully described and sketched on countless so-called Instrument Approach Plates (IAPs), and are available for any airport in the world, provided it has the appropriate navigation facilities installed. All IAPs were developed with one simple goal in mind: Give the pilot a way to descend through any meteorological conditions to a precise place and altitude from where a safe, visual landing can be accomplished. Generally speaking, there are two types of instrument approach procedures: precision and non-precision approaches. Non-precision approaches are those where only horizontal navigation information is available. This means that the pilot can see by scanning his instruments how well he is aligned with the landing runway. He is completely on his own, however, in maintaining the prescribed altitude levels (Minimum Safe Altitudes) at any time during the approach. The most common non-precision approaches are VOR and NDB approaches. Precision approaches add a vertical navigation information through an electronic glidepath that can be visualized on the cockpit instruments. They are the safest instrument approaches as the pilot has a constant feedback on the current altitude situation right before his eyes. The most common precision approach is the ILS approach. Each type of approach, whether precision or non-precision, can be split up into four segments: Initial Approach, Intermediate Approach, Final Approach and Missed Approach. The Initial Approach begins at the Initial Approach Fix (IAF), which is generally a navaid. At this point the pilot will make the transition from the enroute flight to the actual approach. Sometimes the IAF will be straight above the destination airport itself. In that case the pilot will cross the airport, fly outbound for some 10 miles, and then accomplish a procedure turn to close the landing runway on the appropriate heading. -- page 10 -- The Intermediate Approach is the segment used to set up the proper landing configuration for the aircraft (speed, flaps, spoilers etc.). The aircraft might already be on a direct course towards the landing runway, but it might just as well still fly some 30° off that heading, awaiting interception of the final approach course. The Intermediate Approach is also the pilot's last chance to do eventually needed major corrections to the altitude or aircraft heading. Those corrections will be very difficult to complete afterwards. The Final Approach is the segment between the Final Approach Fix (FAF) and the Missed Approach Point (MAP). Both might be located straight above a navaid (VOR, NDB, marker beacon) or defined by a distance or radial from such a navaid. At the FAF the aircraft is already very close to the runway and starts its last descent towards the touch down zone. On a non-precision approach, the pilot is not allowed to descend below a certain minimum altitude (Minimum Descent Altitude, MDA), which is indicated on his Instrument Approach Plate. If he reaches this altitude before arriving at the MAP, he will have to approach the MAP in level flight. On a precision approach however, the pilot will never transit to level flight. Here the MAP is replaced by an altitude indication called Decision Height (DH). It varies around 200 feet above the touch down zone. If the pilot has not established visual contact to the runway at the DH on a precision approach, or at the MAP on a non-precision approach, he must execute a go-around following the Missed Approach instructions. A Missed Approach Procedure has been carefully designed for every instrument approach. The procedure has one simple goal: get the aircraft quickly and safely out of the dangerous zone near the ground and close to the airport and guide it to a place where it can hold and try another approach as traffic permits. Generally, the Missed Approach will end at the IAF, thus closing the loop of Initial, Intermediate, Final and Missed Approach segments. -- page 11 -- Setting up Final Approach ───────────────────────── Minimum configuration Final Approach requires Windows 3.1, installed on a PC with 386 or higher processor, 2 Mb of RAM (4 Mb recommended) and a VGA or higher graphics adapter. It can make use of any printer supported by Windows. The Visual Basic 2.0 runtime library VBRUN200.DLL must be present in the Windows directory. You can download it from almost any BBS or from CompuServe. Please make sure that you have not erased the Truetype fonts "Arial" and "Times New Roman" that are included with Windows 3.1. Final Approach makes heavy use of them and will not run without. Installation Copy the files included in FINALA.ZIP to any directory of your hard disk. They will take up below 350K. Running Final Approach ────────────────────── Recommended procedure: Install Final Approach permanently into one of your Windows program groups. To do so, start Windows, then within Program Manager choose File - New - Program Item and enter a description, the path and filename and the working directory (important!) where you have FINALAPP.EXE installed. From that moment on, you can run the program by double-clicking on the Final Approach icon. or From the DOS command line, change to the Final Approach directory ad type "finalapp" <ENTER>. Windows will be autostarted and the Final Approach opening screen will appear. or From within the Windows Program Manager, choose File - Run..., then type the path and name of FINALAPP.EXE on the command line. Click OK. -- page 12 -- Quick Start ─────────── When you start the program and have passed the opening screen you'll see an empty Instrument Approach Plate with two rows of buttons to the right of it. For a first impression you should load and print some of the IAPs that come with the program. To load an IAP, select the <LOAD> button. The IAPs are based on data files with the extension *.IAP. Several IAPs are included with the program. Highlighting any of the *.IAP files in the file list window will display its header information in the small picture box below: map/airport name, approach type and runway. Select the one you want to retrieve and click <OK>. Once an IAP is displayed you can print it, copy it to the Windows Clipboard or edit it directly on screen. The "Switch to Profile View" button opens a second window with the glidepath for the approach. Important note: Please remember that the unregistered version will show and print a default profile only, that is in no way related to the currently loaded IAP. Maybe you want to try your hand at designing an own IAP, without reading through the whole documentation first. You should encounter no major problems. First select <NEW> to remove the eventually loaded IAP from the screen. The design buttons are all conveniently placed in the left row, close to the drawing canvas, and are arranged in logical order. Try them one by one, use the <Give model> and <Help> buttons where available and above all: Keep an eye on the status line below the drawing canvas! -- page 13 -- The buttons explained ───────────────────── Both plan view and profile view display two vertical rows of buttons. The buttons in the left row differ between the plan view window and the profile view window. They are all used to draw the elements of your IAP and will be discussed below. See "Design Buttons - Plan View" and "Design Buttons - Profile View" for details. If you use Final Approach only to display and/or print IAPs designed by other users, you may skip the following two sections, as you will work with the right button row only. The right-hand buttons are covered later in this documentation under "Right-hand buttons". To switch beween plan and profile view, select the coloured button labeled "Switch to Profile View" or "Switch to Plan View" located above the button rows. Design Buttons - Plan View ────────────────────────── <BASIC> Clicking the <BASIC> button opens a dialogue window, in which you define the header of your IAP (city, airport and approach name, elevation, frequencies etc). Before entering your data you may click the <Give model> button. It will write default values into all fields, providing an idea of what Final Approach expects. Then, as you tab from field to field, you can simply overwrite those values with the appropriate data for your plate. If you want more detailed information, pressing the <Help> button will start the Windows Help engine with the <BASIC> topic preselected. Let's have a look now at the different fields, giving an example for each. - Map Name: location of the airport (ex: SEATTLE, WASH) - Airport: name of the airport (ex: TACOMA INTL) - Approach: type of approach and runway (ex: VOR Rwy 34L) - Main Nav: type, frequency and identifier of the navaid the approach is based on (ex: VOR 116.8 SEA) - Apt. Elev.: Elevation in feet above MSL, number only (ex: 429) -- page 14 -- - Cant Angle: Number with optional negative sign (ex: 5 or -5). Because of the geographic difference between Magnetic North and True North the headings on an IAP are generally canted one way or another. If you have an original IAP at hand, you can easily see that a line pointing North is not always going straight up, as one might suppose, but that it points more or less to the top left or right. The Cant Angle allows you to replicate this on your IAP. For those who use Microsoft Flight Simulator, there is an easy way to evaluate the exact FS Cant Angle. Position your aircraft at the airport you are designing an IAP for, switch into slew mode and press the ALT key several times. Your aircraft will then be directed straight to FS4 North, the gyro showing the opposite of the current Cant Angle. As an example, 352 on the gyro would indicate a Cant Angle of 8 , whereas 012 would correspond to a Cant Angle of -12 . If you enter a positive number, the runway, approach line, holding and VORs will be canted forward by as many degrees, a negative number will cant them backward. Final Approach accepts values between -40 and 40 degrees. - Frequencies: If a frequency is not available, just leave the corresponding field blank, else type the frequency (ex: 118.45) - FS Coordinates: Final Approach will accept values up to 65536 for both North and East coordinates. If you do enter values in these fields, they will show up just below the bottom line of the IAP as it is printed. - Scenery info: Enter a short indication of the scenery required (or that you would recommend) for actually flying the approach in the simulator. If available, this memo will be printed below the bottom line of the IAP. Availability: Available any time. If you decide to change a value later, simply reselect <BASIC>. <RUNWAY> First define the desired runway heading by moving the horizontal scroll bar with the mouse, the cursor keys (1 degree increments) or PgUp/PgDn (10 degree increments). Click <OK>. The windows closes. Now place the runway threshold by clicking at the appropriate location on the drawing canvas. The runway is automatically canted to match the Cant Angle set in the plan view <BASIC> dialogue. Availability: Available any time. If you decide to change the runway heading or location, simply reselect <RUNWAY>. Important note: Redoing the runway will erase the approach line, the Outer Marker and eventual intersections you may already have drawn! Final Approach will warn you accordingly. -- page 15 -- <APPROACH> Clicking the <APPROACH> button opens a dialogue window in which you define the approach heading, which defaults to runway heading. Change it by moving the horizontal scroll bar with the mouse, the cursor keys (for 1 degree increments) or PgUp/PgDn (for 10 degree increments). You have several more options: - Select "Procedure Turn left" or "Procedure Turn right" to include the procedure turn symbol at the beginning of the approach line. - Check "Localizer" for an appropriate representation of the localizer symbol used for an ILS-approach. - Check "Middle Marker" to have the elliptical Middle Marker symbol drawn slightly ahead of the runway threshold. Click <OK>. The windows closes. Now click on the drawing canvas to define the length of the approach line (the distance between the start of the approach line and the runway threshold). Sounds complicated, but is quite handy, once you understand how it is done. Example: Suppose you have defined an approach heading of 090°. Now click at one inch from the runway threshold (anywhere in an 360° circle around it). The approach line will then start at exactly one inch from the runway threshold, but automatically aligned to the 090° heading that you defined in the dialogue window. The approach line is canted automatically to match the Cant Angle set in the plan view <BASIC> dialogue. Availability: Available any time, once a runway is present. If you decide to change the approach line settings or length, simply reselect <APPROACH>. Important note: Redoing the approach will erase the Outer Marker and all eventual intersections you may already have drawn! Again, Final Approach will warn you accordingly, if one of these elements is present on your IAP. -- page 16 -- <OUTER MARKER> After selecting <OUTER MARKER> you may click on the drawing canvas to define the distance between the runway threshold and the Outer Marker beacon. See the example above for details. The elliptical Outer Marker symbol is automatically centered onto the approach line, even if you click outside. If the distance you indicate with your mouseclick is longer than the approach line, the Outer Marker is placed at the very end of the approach line. Availability: Available any time, once an approach line is present. If you decide to change the location of the Outer Marker, simply reselect <OUTER MARKER>. The old Outer Marker will then be erased and you can define a new one. <INTERSECTIONS> After selecting <INTERSECTIONS> you are offered two options: If you want the intersection to automatically snap to the approach line, select "place within approach line". You may then click on the drawing canvas to define the distance between the runway threshold and the desired intersection. The intersection symbol (a small triangle) will be automatically centered onto the approach line, even if you click outside. If the distance you indicate with your mouseclick is longer than the approach line, the intersection symbol will be placed at the very end of the approach line. If you select "allow free placement" however, the intersection will simply appear centered around the location of your next mouseclick. A maximum of three intersections is allowed. If you accidentally misplaced one, select <UNDO> before placing any other element. Availability: Available only if an approach line is present and until the three intersections have been drawn. -- page 17 -- <HOLDING> A word of explanation first: The beginning of the holding pattern is referred to as "holding fix". This holding fix can be located straight above a navigation facility such as a VOR or NDB, or be defined by intersecting radials from two different VORs. Holding direction is the direction towards the holding fix (the so- called inbound course). Immediately after passing the holding fix, the pilot engages a standard-rate 180° left or right turn that brings the aircraft to the outbound course in exactly a minute. The <HOLDING> button leads to a dialogue window in which you define the holding direction and set the holding options. The holding direction defaults to approach heading. You can change it by moving the horizontal scroll bar with the mouse, the cursor keys (for 1 degree increments) or PgUp/PgDn (for 10 degree increments). You have two more options: - Select "Draw intersection symbol at holding fix" to place a triangular intersection symbol at the location of the holding fix. Activate this feature only if your holding fix is defined by two intersecting radials. Leave it unchecked if the holding fix is located above a VOR or NDB. - Decide whether your holding pattern requires right or left turns and activate one of the radio buttons accordingly. Press <OK>. The windows closes. Now click on the drawing canvas to position the holding fix, i.e. the point where the first left or right turn begins. Availability: Available any time. If you want to change the holding direction, position or options, simply reselect <HOLDING>. <VOR> Select <VOR> to place the symbol for that navigation facility on your plate. This symbol is canted automatically to match the Cant Angle set in the plan view <BASIC> dialogue. A maximum of three VORs is allowed. Place the center of the symbol by clicking at the desired location on the drawing canvas. If you accidentally misplaced it, select <UNDO> before placing any other element. Availability: Available until the three VORs have been drawn. -- page 18 -- <NDB> Select <NDB> to place the symbol for that navigation facility on your plate. A maximum of three NDBs is allowed. Place the center of the symbol by clicking at the desired location on the drawing canvas. If you accidentally misplaced it, select <UNDO> before placing any other element. Availability: Available until the three NDBs have been drawn. <LINES> On an IAP, lines symbolize VOR radials and define intersections. Therefore Final Approach expects each line to be attached to a VOR, intersection or the holding fix. A total of six lines is allowed. Select <LINES>, decide which element to attach the line to, then click <OK>. The line will start at the element you selected. Now click on the drawing canvas to define the other end of the line. If you accidentally misplaced a line, select <UNDO> before placing any other element. Availability: Available until the six lines have been drawn. Note: If you are unsure which one of your VORs or intersections is nr. 1, 2 or 3, select the checkbox labeled "Show Numbers" to the lower right of your screen. All VORs and intersections on the plate will then display their running number. -- page 19 -- <FREE TEXT> Select <FREE TEXT> to place up to twelve formatted text strings of 1 to 3 lines each on the chart. In a dialogue window, you may type the text to display on each line, define the desired point size and whether you want the text bold or regular. Now click <OK> and place the text by clicking at the appropriate location on the drawing canvas. The first text line will start to the immediate right of your mouseclick. If the text doesn't fit (wrong point size or length) or you misplaced it, select <UNDO> before placing any other element. Then reselect <FREE TEXT>. Your old text string will still be there, so you can easily change point size, attribute and location. Availability: Available until all twelve text strings have been placed. <NAVAID BOX> VORs and NDBs are generally identified by shadowed boxes, containing the frequency and the two- or three-letter-code of the facility. Examples of this would be "113.6 LAX" for a VOR or "327 AY" for an NDB. Select <NAVAID BOX> to place up to six navaid boxes on the plate. In a dialogue window, you may type the text to display, define the desired point size and whether you want the text bold or regular. The recommended text size and attributes (10 point bold) are preset by default. If you respect two simple rules, Final Approach will automatically include the appropriate morse id in the navaid box: Just put the station id last and write it in all uppercase letters. So "113.6 LAX" will generate a morse code while "113.6 Lax" or "LAX 113.6" will not. Click <OK> and place the box by clicking at the appropriate location on the drawing canvas. Your mouseclick will correspond to the upper left corner of the box. The box size will automatically adapt to the displayed text height and width. Text and morse code will appear centered within the box. If the box doesn't fit or you misplaced it, select <UNDO> before placing any other element. Then reselect <NAVAID BOX>. Your old text string will still be there, so you can easily change point size, attribute or location. Availability: Available until the six navaid boxes have been drawn. -- page 20 -- <ILS BOX> ILS approaches are generally identified by unshadowed, rounded boxes displaying the approach heading, the frequency and the four-letter-code of the ILS. An example would be "140° 109.7 IORD". Select <ILS BOX> to place such a box on the plate. In a dialogue window, you may type the text to display, define the desired point size and whether you want the text bold or regular. 12 point bold is recommended and preset by default. If you respect two simple rules, Final Approach will automatically include the appropriate morse id in the ILS box: Just put the localizer id last and write it in four uppercase letters. So "353° 109.1 IPIE" will generate a morse code id while "353° 109.1 I-PIE" will not. Click <OK> and place the box by clicking at the appropriate location on the drawing canvas. Your mouseclick will correspond to the upper left, rounded corner of the box. The box size will automatically adapt to the displayed text height and width. If it doesn't fit or you misplaced it, select <UNDO> before placing any other element. Then reselect <ILS BOX>. Your old text string will still be there, so you can easily change point size, attribute or location. Availability: Available any time. If you decide to change the box text, settings or location, simply reselect <ILS BOX>. The ILS Box will be erased and you can then define and place a new one. -- page 21 -- Design Buttons - Profile View ───────────────────────────── <BASIC> Clicking the <BASIC> button opens a dialogue window where you enter the data to be displayed below the approach profile. Before entering your data you may click the <Give model> button. It will feed default values into all text fields. Those default values are the program's best guess about the data you are likely to use for your approach plate and should at least come pretty close. If no guess is possible, the default data that appears can simply be used as a model on which to base your own data input. If you want more detailed information, pressing the <Help> button will start the Windows Help engine with the <BASIC> topic preselected. Let's examine the fields one by one: - TDZE Elev.: Touch Down Zone Elevation. On most airports, the exact elevation of each runway's touch down zone will slightly differ from the general airport elevation. The <Give model> button defaults to the airport elevation you entered in plan view. Enter the number in feet above Mean Sea Level (MSL). - Straight-In: Enter the Minimum Descent Altitude (MDA) for a straight- in VOR or NDB approach or the Decision Height (DH) in case of an ILS approach. The program defaults to a rounded 400 feet above airport elevation. Enter the number in feet above Mean Sea Level. Final Approach will determine which kind of approach you are designing and automatically add "MDA" or "DH" in front of the number when the plate is displayed or printed. If no straight-in landing is available, leave the field blank. The IAP will then display "NA" (not applicable). - 90, 120, 140, 165 kts: circling approach minimum descent altitudes according to aircraft types with specified maximum circling speeds. Final Approach defaults to a rounded 600 feet above airport elevation for 90 kt aircraft, 640 feet for 120 and 140 kt aircraft and 720 feet for 165 kt aircraft. If no circling approach is available, leave the fields blank. The IAP will then display "NA" (not applicable). -- page 22 -- - Timing Distance: Length of the Final Approach segment in nautical miles. In other words, the distance separating the Final Approach Fix (FAF) from the Missed Approach Point (MAP). Final Approach uses this number to calculate and display the exact timing in minutes and seconds from the FAF to the MAP. The default value via <Give model> has been set arbitrarily to 4.5, which would seem a good average value. If you leave this field blank, no timing information will be displayed. - Timing Label: Text string that will be displayed in front of the timing distance indication (ex. "OSTOR to MAP" or "MAP at VOR") - Missed Approach: Detailed missed approach instructions to be displayed below the approach profile. The text length is limited to 256 characters (spaces included). If you enter a longer text, the exceeding characters will be cut off. Availability: Available any time. If you decide to change a value later, simply reselect <BASIC>. <GLIDESLOPE> The glideslope symbol is used for ILS approaches only. It displays as a wide open arrow that starts at the point where the aircraft is supposed to intercept the glidepath and ends at the touch down zone of the runway. Click to place the upper end of the glideslope, i.e. the point where the descent to the runway is supposed to begin. If you will use the "Snap to Grid" function to draw the glidepath, it is recommended to already activate it as you place the glideslope. That way it will be much easier to let your descending glidepath segment coincide exactly with the glideslope symbol. Note that the grid includes a guideline for standard 3° descents, that can be quite useful when placing the glideslope. Availability: Available any time. If you want to redo the glideslope symbol, simply reselect <GLIDESLOPE>. The old symbol will be erased and you may place a new one. -- page 23 -- <GLIDEPATH> Before you begin drawing the different glidepath segments, it would be a good idea to activate the "Snap to Grid" function as this will facilitate the drawing of perfectly straight segments. As you click the <GLIDEPATH> button, a big button labeled <GLIDEPATH FINISHED> will appear above the drawing canvas. You will use it when you have finished defining the glidepath segments. The glidepath should be drawn in the same direction it will be flown later. The first mouseclick will set the starting point for the first segment, marked for your reference by a small, red circle, that will be erased automatically once you finish designing the glidepath. Every subsequent mouseclick will place a visible segment, the next always connecting to the previous one. A maximum of ten consecutive mouseclicks (i.e. 9 segments) is allowed. While in the drawing process, a multi-level Undo is available. The <UNDO> button will take you one step back at a time, erasing the last segments drawn one by one. Click the <GLIDEPATH FINISHED> button when you are done. Final Approach will then remove the reference circle mentioned above and complete the glidepath by adding a short segment with an arrow pointing upward in the direction of an eventual overshoot. Availability: Available any time. If a glidepath is already present, reselecting <Glidepath> will open a dialogue window, asking if you want to redo this glidepath. If you confirm, the glidepath will be erased and you will be placed into drawing mode. <INTERSECTION> 3 intersection symbols (dashed, vertical lines) are available. They will run up from the bottom of the drawing canvas to the location of your mouseclick. Click to define the top end of such a symbol. Remember not to draw the intersection symbols too high up, as you will need some space above for the text label you will add later. Availability: Available until all three intersections have been placed. -- page 24 -- <MARKER> The marker symbol differs from the intersection symbol by its triangular shape. It starts as a single line at the bottom of the drawing canvas, then gets much larger at the top end. Final Approach offers 2 identical markers. One could be used to symbolize the Outer Marker, the other for the Middle Marker. Click on the drawing canvas to define the top center of a marker symbol. Again, don't draw the symbols too high up, as you will probably want to put an appropriate label above later. Availability: Available until both markers have been placed. <VOR> The VOR symbol starts as a single line at the bottom of the drawing canvas and gets slightly larger at the top end. As no further indications are required, the label "VOR" is drawn automatically above. Click on the drawing canvas to define the top center of the symbol. Availability: Available any time. If you want to redo the VOR symbol, simply reselect <VOR>. The old symbol will be erased and you may place a new one. <NDB> The NDB symbol is identical to the VOR symbol but, obviously, the label "NDB" will be added above. Click on the drawing canvas to define the top center of the symbol. Availability: Available any time. If you want to redo the NDB symbol, simply reselect <NDB>. The old symbol will be erased and you may place a new one. -- page 25 -- <FAF> The <FAF> button will let you add a Final Approach Fix symbol (a small "x") to your glidepath. It indicates the exact location where the final approach segment begins. Click on the drawing canvas to place the center of the symbol. Availability: Available any time. If you want to redo the FAF symbol, simply reselect <FAF>. The old symbol will be erased and you may place a new one. <FIX LABEL> Clicking the <FIX LABEL> button opens a window where you enter the text to be displayed above a marker or intersection symbol. Three buttons in this dialogue window allow to select a standard model for a Middle Marker label, an Outer Marker label or an intersection label. Click one of these buttons and Final Approach will fill enter text strings that should give you an idea of what is expected in the different fields. Then you may overwrite these values with your own. The first line (Textline1) will always be displayed in a larger, bold and italic font, the second and third lines will show as normal text in a somewhat smaller font size. Use the first text line for the name of the intersection (ex: VEALS) or for the indication of a DME distance in case no name is available (ex: D7.5). If you entered a name in the first field, then use the second field to enter the appropriate DME distance. Use the third field to enter the altitude (feet MSL) the aircraft should have reached at this fix. Enter the number only, Final Approach will add "GS" in front of it and the altitude above ground level (AGL) behind it, as the chart is displayed or printed. You may fill in as many text fields as you like (1, 2 or all 3). If you leave any line blank, Final Approach will format the fix label accordingly. The lower line (or lines) will then move up, so that no blank line will be displayed in between. Click <OK>. Your next mouseclick on the drawing canvas will indicate the location of the lower center of the fix label. To place a label above an intersection or marker symbol, click slightly above the top of that symbol. The "Snap to Grid" function should be turned off for best results. Availability: Available until all six labels have been placed. -- page 26 -- <ALTITUDE> For your convenience, Final Approach lets you enter altitude labels via an own button, rather than as free text. After clicking the <ALTITUDE> button you will be asked for the altitude above MSL you wish to enter. Type the appropriate number and click <OK>. Your next mouseclick on the drawing canvas will indicate the beginning of the baseline for the altitude MSL you entered, which allows for a very precise placement above any horizontal glidepath segment. Final Approach will automatically add the corresponding altitude AGL below the altitude MSL you entered. So if you place the altitude MSL slightly above one of the horizonal segments of your glidepath, the altitude AGL will be added below. The "Snap to Grid" function should be turned off for best results. Availability: Available until all four altitude labels have been placed. <FREE TEXT> Select <FREE TEXT> to place up to twelve formatted text strings of 1 to 3 lines each on the profile. In a dialogue window, you may type the text to display on each line, define the desired point size and whether you want the text bold or regular. Then click <OK> and place the text by clicking at the appropriate location on the drawing canvas. The first text line will start to the immediate right of your mouseclick. If the text doesn't fit or you misplaced it, select <UNDO> before placing any other element. Then reselect <FREE TEXT>. Your old text string will still be there, so you can easily change point size, attribute or location. Availability: Available until all twelve text strings have been drawn. -- page 27 -- Right-hand buttons ────────────────── The right button row is identical in plan and profile view. <NEW> If you are designing a plate and get the feeling to have seriously messed-up with your work, select the <NEW> button. It will open a dialogue box, asking whether you want to erase the whole IAP or the profile view only. Because the profile view relies on data from the plan view, the plan view cannot be erased separately. <LOAD> In the file dialogue window, select the IAP to display from the file list. According to Windows conventions, the right list-box lets you switch to another directory. The drive-list box below can be used to change to another drive. <SAVE> Use the <SAVE> button to save an IAP that has already been named. If you select <SAVE> to save an IAP not previously named, the <SAVE AS> dialogue window will open. When designing, remember to save repeatedly. If you mess-up, you can always retrieve the previous version of your work without losing too much of your design. <SAVE AS> This button opens a dialogue window in which you can name or rename your work before saving it to disk. Only DOS-valid characters are allowed. Final Approach prevents you from giving an extension as it will add *.IAP by default. <ABOUT> The <About> button displays information about the version of Final Approach you are using. If you have registered your copy, it will also display your name and address together with your license number. -- page 28 -- <EXIT> If you have unsaved work, selecting <EXIT> will open a message box asking if you are willing to lose the changes you made. Select <NO> if you want to go back and save your work. <PRINT> One of the most important features of Final Approach is its ability to print the approach plates you designed or loaded. You may define a left border between 1 and 3 inches for your printout. The printing routines will always print the IAP as a whole, so that plan and profile view come out combined into a single plate. Please remember that the unregistered version will always load and print a default profile marked "demo only". <CLIPBOARD> This button allows you to copy the drawing from the active window to the Windows Clipboard, so that you can paste it into Paintbrush or a similar program, edit it there and save it in the format you prefer. Selecting <COPY CLPBOARD> from the plan view window will transfer the plan view of the approach, whereas selecting this button from the profile view window will transfer the profile view to the Clipboard. To conserve space, only the contents of the drawing canvas are transferred to the Clipboard, whereas all outside text (heading section and, in case of the profile view, Missed Approach instructions and timing table) are cut off. <UNDO> The <UNDO> button will erase the last element drawn. This is a one- level undo, so be sure to select <UNDO> before placing the next element on the drawing canvas. Only when designing the glidepath will Undo be multi-level and erase the last segments drawn in backward order. If your last action was the deletion of an IAP element via the <ERASE> button, <UNDO> will restore this element to its previous location. -- page 29 -- <ERASE> Elements that can appear only once on each IAP (runway, approach line, Outer Marker, holding, ILS box, glideslope etc.) may be removed simply by reselecting the button used to create them in the first place. The <ERASE> button allows you to remove any of the other IAP elements. It will open a window, listing all multiple elements in the current view. Select one of these by its number and click <ERASE> to remove it from the chart. Understandably, only elements that are actually part of the current IAP are selectabe, the other are greyed-out. If you are unsure about the running number of the element you want to erase, select <CANCEL> to go back to the chart and activate the "Show numbers" checkbox. All multiple elements will then display their running number. Remember that even if you inadvertently erased the wrong element, all is not lost. Just click the <UNDO> button next, and your element will reappear at its original location. <HELP> The <HELP> button starts the Windows Help engine and tries to select the topic you are most likely to refer to. If you are working in plan or profile view, the help index will come up. If you select the <HELP> button from any of the dialogue windows, context-sensitive help on the possible options you have in this window will pop up. -- page 30 -- Checkboxes ────────── "DISPLAY GRID" If this checkbox is selected, a grid will be imposed over your canvas to facilitate the exact placement of objects. In the plan view window, two dashed, blue lines will be visible in the upper left corner of the drawing canvas. They show the space available to design a chart in the 320*200 format required for use as an AAF-PCX. If you want to draw a chart for AAF, fit all elements into this reduced surface, then copy the IAP to the Clipboard. Start Paintbrush, select "Options", "Image Attributes" and set these to a width of 320 and a height of 200 pixels. Now paste the image from the Clipboard, edit it as you like and save it as a *.PCX file. In the profile window, the darker blue horizontal lines could be used as guides when designing the glidepath segments. "SNAP TO GRID" With this checkbox selected, every mouseclick you enter within the drawing canvas will snap to the nearest intersection of grid lines, no matter if the grid is currently visible or hidden. You may activate and deactivate the "Snap to Grid" function as you like, placing some elements with, others without having the function activated. You may even toggle it on or off while designing the glidepath, drawing the horizontal elements with "Snap to Grid", the vertical ones without. "SHOW NUMBERS" For each line you draw in plan view, Final Approach will ask for a connecting point (VOR or intersection). If the checkbox "SHOW NUMBERS" is selected, all multiple elements on the IAP will display their running number, to take the guesswork out of the line placement. "Show numbers" also comes handy when you must select an element to erase by indicating its current number. -- page 31 -- Hints and tips ────────────── Whether you have designed (and hopefully test-flown) an approach procedure by yourself, or whether you are just digitizing a real-world approach plate, here are some hints that might help you work faster and easier. Above all: Read the status line! Whenever you click a button, the status line below the drawing canvas will inform you exactly about the action that will be performed with your next mouseclick onto the drawing canvas. The order in which you place elements can also contribute towards making your life at the drawing board easier. The buttons in the left row have been arranged in logical order from top to bottom. If you select the elements you need, working your way down the left buttonbar, you will be on the safest possible side. If you misplaced an element, select the <Undo> button immediately. <Undo> will always erase the last element drawn, so be sure to erase the faulty element before you draw a new one. Note that all elements can still be redone any time you wish. Single elements (runway, approach line etc.) are removed by reselecting the button used to create them. Multiple elements (free text, navaid boxes, navaids etc) are removed via the <ERASE> button. Make good use of the "Snap to Grid" function. It can be toggled on or off anytime and is completely independent of the "Display Grid" function. You'll probably need it most to align text labels or to draw the horizontal glidepath segments. Don't hesitate to use the <Give model> function in the <BASIC> dialogue both in plan and profile view. It will give you a clue on what data is expected in the different text fields by entering default data strings for you. These can then easily be overwritten with your own data, as you tab from field to field. The degree symbol can be entered by holding down the ALT button while typing 248 on the numeric keypad. Carets (^), if entered as free text and formatted to 14 point bold, make excellent highest obstacle symbols. If not directly available on your keyboard, use ALT-94 to create them. All elements that are not included in the ERASE dialogue window, can be removed by reselecting the button used to create them. If you want to draw lines that are not attached to a VOR, intersection or holding fix, there is an easy workaround: Simply place any of those elements where you want the line to start. Next draw the line, attaching it to that element. Finally, erase the element via the ERASE button or, in case its a holding fix, by reselecting the <HOLDING> button. The line will remain in place. -- page 32 -- Designing consistent Instrument Approach Plates ─────────────────────────────────────────────── If you want to achieve consistent results, be sure not to use random text sizes and attributes for your free text labels and navaid boxes. Here are some rules of thumb to generate clean, readable output: Plan View * Approach heading (140 ): 12 pt bold * Intersection names (CONDY): 10 pt bold * Distance indications for Intersections (D7.5 ILAS): 8 pt normal * Radial numbers defining intersections (032 ): 8 pt normal * Radial labels defining VOR outside IAP: (SBJ 112.3): 8 pt bold * Notice (SIMULT. APPR. AUTHORIZED WITH RWY 27L): 8 pt normal * Navaid Boxes (113.0 OBK): 10 pt bold * ILS Box (316° 109.1 ICMI): 12 pt bold Profile View * Approach heading (140°): 12 pt normal * Distance between intersections (7.5): 8 pt normal * Procedure Turn distance from Airport, first line (10 NM): 10 pt bold * id. second and third line (from VEALS): 10 pt normal * Notice (GLIDESLOPE UNUSABLE BELOW 140 ): 8 pt normal -- page 33 -- File Format ─────────── All IAPs are saved into *.IAP data files. These are pure Ascii-files that can, with a little care, be easily edited with any text editor. Windows Notepad does a perfect job on this. Please be sure to back up the files before manipulating the data they contain. Here's how the data is organized: The first 10 lines are reserved for the IAP header section (Map Name, Airport name, Approach Name, Main Nav, Elevation, Cant Angle, Frequencies). Do not introduce a comma into any of these strings. If you want a comma displayed in the Map Name, the *.IAP file must contain a semicolon instead. Example: For a Map Name like CHICAGO, ILLINOIS, the IAP file would contain CHICAGO; ILLINOIS Apart from the self-documenting lines 1 to 10, all other lines begin with a three-letter identifier used for documentation purposes. All following data on each line is separated by slashes. The first two numbers following the identifier are always the coordinates, i.e. the horizontal and vertical screen position of the element. The position is indicated in twips, where 1440 twips correspond to an inch when drawn on paper. So one twip would be 1/1440 of an inch, which is really close to nothing. Try changes of at least 20 twips or more to see minor changes in the IAP. Example: VOR/00828/00444 would mean that this VOR is placed at 828 twips from the left border and at 444 twips from the top border of the drawing canvas. Important note: To erase an element directly from the data file, set its first coordinate to /00000/. PLAN VIEW ELEMENTS: Map Name Airport name Approach Name Main Nav Elevation Cant Angle ATIS Frequency Approach Frequency Tower Frequency Ground Frequency VOR/x-position/y-position NDB/x-position/y-position RWY=RUNWAY/threshold x-position/threshold y-position/heading -- page 34 -- APP=APPROACH LINE/starting point x-position/starting point y-position /heading/Procedure turn (N, L, R)/Localizer (-1, 0)/Middle marker (-1, 0) OMK=OUTER MARKER/x-position/y-position TXT=FREE TEXT/x-position/y-position/point size/bold (1,0)/string NBX=NAVAID BOX/x-position/y-position/point size/bold (1,0)/string ILS=ILS BOX/x-position/y-position/point size/bold (1,0)/string INT=INTERSECTION/x-position/y-position LNE=LINE/starting point x-position/starting point y-position/ending point x-position/ending point y-position PROFILE VIEW ELEMENTS: TDZ=Touch-Down-Zone-Elevation STR=Straight-In Minimum Altitude CRA=Circle-to-Land Altitude for CAT A CRB=Circle-to-Land Altitude for CAT B CRC=Circle-to-Land Altitude for CAT C CRD=Circle-to-Land Altitude for CAT D TDI=Timing Distance Timing Label Missed Approach Instructions Do not introduce a comma into the Missed Approach Instructions. If you want a comma displayed, the *.IAP file must contain a semicolon instead. GLI=GLIDEPATH coordinates/x-position/y-position PVR=VOR/x-position/y-position PND=NDB/x-position/y-position PMK=MARKER/x-position/y-position FAF=FINAL APPROACH FIX/x-position/y-position GSL=GLIDESLOPE/x-position/y-position LBL=LABEL/x-position/y-position LN1=Line1 of this label LN2=Line2 of this label LN3=Line3 of this label PIN=INTERSECTION/x-position/y-position ALT=ALTITUDE LABEL/x-position/y-position/altitude PTX=FREE TEXT/x-position/y-position/point size/bold (1,0)/string NEW VERSION 2.1 ELEMENTS: FSN=Flight Simulator North coordinate FSE=Flight Simulator East coordinate SCN=Required Scenery memo -- page 35 -- Comments ──────── Any bug reports, suggestions or comments are of course most welcome. If you are a CompuServe member, please address them to the following ID: Georges Lorsche 100041,211. Send them as email or let's discuss them publicly in the FSFORUM. Hope you enjoy this program! Disclaimer ────────── Author and distributor make no warranty of any kind, express or implied, including without limitation any warranties of merchantability and/or fitness for a particular purpose. We shall not be liable for any damages, whether direct, indirect, special or consequential arising from a failure of this program to operate in the manner desired by the user. We shall not be liable for any damage to data or property which may be caused directly or indirectly by the use of this program. IN NO EVENT WILL WE BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF YOUR USE OR INABILITY TO USE THE PROGRAM, OR FOR ANY CLAIM BY ANY OTHER PARTY. ───────────────────────────────────────────────────────────────────────── Microsoft (R) is a registered trademark of Microsoft Corporation. Windows (TM) is a trademark of Microsoft Corporation. Flight Simulator (R) is a registered trademark of Sublogic Corporation. Aircraft & Scenery Designer (TM) is a product of the Bruce Artwick Organization, Ltd. and published by Microsoft Corporation. Aircraft and Adventure Factory (TM) is a product of the Bruce Artwick Organization, Ltd. and published by Mallard Software, Inc.